Graphical and text based co-design editor for industrial automation projects

ABSTRACT

An industrial IDE supports development of control programming using an industrial domain-specific language (DSL) that allows control programming to be written using a scripted programming language having features catered to the industrial domain. The industrial DSL can simplify and streamline development of industrial control code relative to using conventional graphics-based control programming formats such as ladder logic, since a script-based industrial DSL can be used to write programming code using fewer mouse clicks relative to traditional control programming environments. Editing tools inherent to the industrial DSL can provide dynamic programming feedback that guides the developer through the process of developing control code. A development interface of the industrial IDE can comprises two editing windows that render the control program in a graphical format and in a text-based format simultaneously, allowing the user to edit the program in either format on the same interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to, U.S.patent application Ser. No. 17/480,669, filed on Sep. 21, 2021, andentitled “GRAPHICAL AND TEXT BASED CO-DESIGN EDITOR FOR INDUSTRIALAUTOMATION PROJECTS,” the entirety of which is incorporated herein byreference.

BACKGROUND

The subject matter disclosed herein relates generally to industrialautomation systems, and, for example, to industrial programmingdevelopment platforms

BRIEF DESCRIPTION

The following presents a simplified summary in order to provide a basicunderstanding of some aspects described herein. This summary is not anextensive overview nor is intended to identify key/critical elements orto delineate the scope of the various aspects described herein. Its solepurpose is to present some concepts in a simplified form as a prelude tothe more detailed description that is presented later.

In one or more embodiments, a system for developing industrial controlprogramming is provided, comprising a user interface componentconfigured to render an integrated development environment (IDE)interface and to receive, via interaction with the IDE interface,industrial control programming input that defines an industrial controlprogram; and a project generation component configured to generate,based on the industrial control programming input, an executable controlprogram file that, in response to execution on an industrial controller,causes the industrial controller to monitor and control an industrialautomation system in accordance with the industrial control program,wherein the IDE interface simultaneously displays a graphical editorwindow that renders the industrial control program in a graphicalformat, and a text editor window that renders the industrial controlprogram in a text-based format, and the IDE interface is configured toreceive the industrial control programming input in a graphical formatvia interaction with the graphical editor window and in a text-basedformat via interaction with the text editor window.

Also, one or more embodiments provide a method for programmingindustrial systems, comprising rendering, by a system comprising aprocessor, an integrated development environment (IDE) interface on aclient device; receiving, by the system via interaction with the IDEinterface, industrial control programming input that defines anindustrial control program; generating, by the system based on theindustrial control programming input, an executable control program filethat, in response to execution on an industrial controller, causes theindustrial controller to monitor and control an industrial machine inaccordance with the industrial control program, wherein the renderingcomprises simultaneously displaying on the IDE interface: a graphicaleditor window that renders the industrial control program in a graphicalformat, and a text editor window that renders the industrial controlprogram in a text-based format, and the receiving comprises: receiving afirst portion of the industrial control programming input in a graphicalformat via interaction with the graphical editor window, and receiving asecond portion of the industrial control programming in a text-basedformat via interaction with the text editor window.

Also, according to one or more embodiments, a non-transitorycomputer-readable medium is provided having stored thereon instructionsthat, in response to execution, cause a system to perform operations,the operations comprising rendering an integrated developmentenvironment (IDE) interface on a client device; receiving, viainteraction with the IDE interface, industrial control programming inputthat defines an industrial control program; generating, based on theindustrial control programming input, an executable control program filethat, in response to execution on an industrial controller, causes theindustrial controller to monitor and control an industrial automationsystem in accordance with the industrial control program, and whereinthe rendering comprises simultaneously displaying on the IDE interface:a graphical editor window that renders the industrial control program ina graphical format, and a text editor window that renders the industrialcontrol program in a text-based format, and the receiving comprises:receiving a first portion of the industrial control programming input ina graphical format via interaction with the graphical editor window, andreceiving a second portion of the industrial control programming in atext-based format via interaction with the text editor window.

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative of various ways which can be practiced, all of which areintended to be covered herein. Other advantages and novel features maybecome apparent from the following detailed description when consideredin conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example industrial control environment.

FIG. 2 is a block diagram of an example integrated developmentenvironment (IDE) system.

FIG. 3 is a diagram illustrating a generalized architecture of anindustrial IDE system.

FIG. 4 is a diagram illustrating several example automation objectproperties that can be leveraged by the IDE system in connection withbuilding, deploying, and executing a system project.

FIG. 5 is a diagram illustrating example data flows associated withcreation of a system project for an automation system being designedusing an industrial IDE system.

FIG. 6 is a diagram illustrating an example system project thatincorporates automation objects into a project model.

FIG. 7 is a diagram illustrating commissioning of a system project.

FIG. 8 is a diagram illustrating control programming using an industrialDSL and compilation of the DSL programming to yield executableindustrial code.

FIG. 9 a is an example automation object namespace hierarchy that can besupported by some embodiments of the industrial DSL.

FIG. 9 b is another example automation object namespace hierarchy forcontrol application elements, which can be supported by some embodimentsof the namespace DSL.

FIG. 10 is a diagram illustrating customization of the IDE system'sprogramming interface.

FIG. 11 is a block diagram illustrating components of an example editordefinition component.

FIG. 12 is a diagram representing the relationship between a graphicalversion of an industrial control program and a corresponding textversion of the program.

FIG. 13 is an example development interface that can be rendered by auser interface component for development of industrial control programs.

FIG. 14 is a diagram illustrating an example architecture in whichcloud-based IDE services are used to develop and deploy industrialapplications to a plant environment.

FIG. 15 is a flowchart of an example methodology for rendering anindustrial control program in an industrial IDE development interfaceand receiving edits to the program.

FIG. 16 is a flowchart of an example methodology for customizing aprogramming interface of an industrial IDE.

FIG. 17 is an example computing environment.

FIG. 18 is an example networking environment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding thereof. It may be evident, however, that the subjectdisclosure can be practiced without these specific details. In otherinstances, well-known structures and devices are shown in block diagramform in order to facilitate a description thereof.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “controller,” “terminal,” “station,” “node,”“interface” are intended to refer to a computer-related entity or anentity related to, or that is part of, an operational apparatus with oneor more specific functionalities, wherein such entities can be eitherhardware, a combination of hardware and software, software, or softwarein execution. For example, a component can be, but is not limited tobeing, a process running on a processor, a processor, a hard disk drive,multiple storage drives (of optical or magnetic storage medium)including affixed (e.g., screwed or bolted) or removable affixedsolid-state storage drives; an object; an executable; a thread ofexecution; a computer-executable program, and/or a computer. By way ofillustration, both an application running on a server and the server canbe a component. One or more components can reside within a processand/or thread of execution, and a component can be localized on onecomputer and/or distributed between two or more computers. Also,components as described herein can execute from various computerreadable storage media having various data structures stored thereon.The components may communicate via local and/or remote processes such asin accordance with a signal having one or more data packets (e.g., datafrom one component interacting with another component in a local system,distributed system, and/or across a network such as the Internet withother systems via the signal). As another example, a component can be anapparatus with specific functionality provided by mechanical partsoperated by electric or electronic circuitry which is operated by asoftware or a firmware application executed by a processor, wherein theprocessor can be internal or external to the apparatus and executes atleast a part of the software or firmware application. As yet anotherexample, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,the electronic components can include a processor therein to executesoftware or firmware that provides at least in part the functionality ofthe electronic components. As further yet another example, interface(s)can include input/output (I/O) components as well as associatedprocessor, application, or Application Programming Interface (API)components. While the foregoing examples are directed to aspects of acomponent, the exemplified aspects or features also apply to a system,platform, interface, layer, controller, terminal, and the like.

As used herein, the terms “to infer” and “inference” refer generally tothe process of reasoning about or inferring states of the system,environment, and/or user from a set of observations as captured viaevents and/or data. Inference can be employed to identify a specificcontext or action, or can generate a probability distribution overstates, for example. The inference can be probabilistic—that is, thecomputation of a probability distribution over states of interest basedon a consideration of data and events. Inference can also refer totechniques employed for composing higher-level events from a set ofevents and/or data. Such inference results in the construction of newevents or actions from a set of observed events and/or stored eventdata, whether or not the events are correlated in close temporalproximity, and whether the events and data come from one or severalevent and data sources.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom the context, the phrase “X employs A or B” is intended to mean anyof the natural inclusive permutations. That is, the phrase “X employs Aor B” is satisfied by any of the following instances: X employs A; Xemploys B; or X employs both A and B. In addition, the articles “a” and“an” as used in this application and the appended claims shouldgenerally be construed to mean “one or more” unless specified otherwiseor clear from the context to be directed to a singular form.

Furthermore, the term “set” as employed herein excludes the empty set;e.g., the set with no elements therein. Thus, a “set” in the subjectdisclosure includes one or more elements or entities. As anillustration, a set of controllers includes one or more controllers; aset of data resources includes one or more data resources; etc.Likewise, the term “group” as utilized herein refers to a collection ofone or more entities; e.g., a group of nodes refers to one or morenodes.

Various aspects or features will be presented in terms of systems thatmay include a number of devices, components, modules, and the like. Itis to be understood and appreciated that the various systems may includeadditional devices, components, modules, etc. and/or may not include allof the devices, components, modules etc. discussed in connection withthe figures. A combination of these approaches also can be used.

FIG. 1 is a block diagram of an example industrial control environment100. In this example, a number of industrial controllers 118 aredeployed throughout an industrial plant environment to monitor andcontrol respective industrial systems or processes relating to productmanufacture, machining, motion control, batch processing, materialhandling, or other such industrial functions. Industrial controllers 118typically execute respective control programs to facilitate monitoringand control of industrial devices 120 making up the controlledindustrial assets or systems (e.g., industrial machines). One or moreindustrial controllers 118 may also comprise a soft controller executedon a personal computer or other hardware platform, or on a cloudplatform. Some hybrid devices may also combine controller functionalitywith other functions (e.g., visualization). The control programsexecuted by industrial controllers 118 can comprise substantially anytype of code capable of processing input signals read from theindustrial devices 120 and controlling output signals generated by theindustrial controllers 118, including but not limited to ladder logic,sequential function charts, function block diagrams, or structured text.

Industrial devices 120 may include both input devices that provide datarelating to the controlled industrial systems to the industrialcontrollers 118, and output devices that respond to control signalsgenerated by the industrial controllers 118 to control aspects of theindustrial systems. Example input devices can include telemetry devices(e.g., temperature sensors, flow meters, level sensors, pressuresensors, etc.), manual operator control devices (e.g., push buttons,selector switches, etc.), safety monitoring devices (e.g., safety mats,safety pull cords, light curtains, etc.), and other such devices. Outputdevices may include motor drives, pneumatic actuators, signalingdevices, robot control inputs, valves, pumps, and the like.

Industrial controllers 118 may communicatively interface with industrialdevices 120 over hardwired or networked connections. For example,industrial controllers 118 can be equipped with native hardwired inputsand outputs that communicate with the industrial devices 120 to effectcontrol of the devices. The native controller I/O can include digitalI/O that transmits and receives discrete voltage signals to and from thefield devices, or analog I/O that transmits and receives analog voltageor current signals to and from the devices. The controller I/O cancommunicate with a controller's processor over a backplane such that thedigital and analog signals can be read into and controlled by thecontrol programs. Industrial controllers 118 can also communicate withindustrial devices 120 over a network using, for example, acommunication module or an integrated networking port. Exemplarynetworks can include the Internet, intranets, Ethernet, DeviceNet,ControlNet, Data Highway and Data Highway Plus (DH/DH+), Remote I/O,Fieldbus, Modbus, Profibus, wireless networks, serial protocols, and thelike. The industrial controllers 118 can also store persisted datavalues that can be referenced by their associated control programs andused for control decisions, including but not limited to measured orcalculated values representing operational states of a controlledmachine or process (e.g., tank levels, positions, alarms, etc.) orcaptured time series data that is collected during operation of theautomation system (e.g., status information for multiple points in time,diagnostic occurrences, etc.). Similarly, some intelligentdevices—including but not limited to motor drives, instruments, orcondition monitoring modules—may store data values that are used forcontrol and/or to visualize states of operation. Such devices may alsocapture time-series data or events on a log for later retrieval andviewing.

Industrial automation systems often include one or more human-machineinterfaces (HMIs) 114 that allow plant personnel to view telemetry andstatus data associated with the automation systems, and to control someaspects of system operation. HMIs 114 may communicate with one or moreof the industrial controllers 118 over a plant network 116, and exchangedata with the industrial controllers to facilitate visualization ofinformation relating to the controlled industrial processes on one ormore pre-developed operator interface screens. HMIs 114 can also beconfigured to allow operators to submit data to specified data tags ormemory addresses of the industrial controllers 118, thereby providing ameans for operators to issue commands to the controlled systems (e.g.,cycle start commands, device actuation commands, etc.), to modifysetpoint values, etc. HMIs 114 can generate one or more display screensthrough which the operator interacts with the industrial controllers118, and thereby with the controlled processes and/or systems. Exampledisplay screens can visualize present states of industrial systems ortheir associated devices using graphical representations of theprocesses that display metered or calculated values, employ color orposition animations based on state, render alarm notifications, oremploy other such techniques for presenting relevant data to theoperator. Data presented in this manner is read from industrialcontrollers 118 by HMIs 114 and presented on one or more of the displayscreens according to display formats chosen by the HMI developer. HMIsmay comprise fixed location or mobile devices with either user-installedor pre-installed operating systems, and either user-installed orpre-installed graphical application software.

Some industrial environments may also include other systems or devicesrelating to specific aspects of the controlled industrial systems. Thesemay include, for example, a data historian 110 that aggregates andstores production information collected from the industrial controllers118 or other data sources, device documentation stores containingelectronic documentation for the various industrial devices making upthe controlled industrial systems, inventory tracking systems, workorder management systems, repositories for machine or process drawingsand documentation, vendor product documentation storage, vendorknowledgebases, internal knowledgebases, work scheduling applications,or other such systems, some or all of which may reside on an officenetwork 108 of the industrial environment.

Higher-level systems 126 may carry out functions that are less directlyrelated to control of the industrial automation systems on the plantfloor, and instead are directed to long term planning, high-levelsupervisory control, analytics, reporting, or other such high-levelfunctions. These systems 126 may reside on the office network 108 at anexternal location relative to the plant facility, or on a cloud platformwith access to the office and/or plant networks. Higher-level systems126 may include, but are not limited to, cloud storage and analysissystems, big data analysis systems, manufacturing execution systems,data lakes, reporting systems, etc. In some scenarios, applicationsrunning at these higher levels of the enterprise may be configured toanalyze control system operational data, and the results of thisanalysis may be fed back to an operator at the control system ordirectly to a controller 118 or device 120 in the control system.

The various control, monitoring, and analytical devices that make up anindustrial environment must be programmed or configured using respectiveconfiguration applications specific to each device. For example,industrial controllers 118 are typically configured and programmed usinga control programming development application such as a ladder logiceditor (e.g., executing on a client device 124). Using such developmentplatforms, a designer can write control programming (e.g., ladder logic,structured text, function block diagrams, etc.) for carrying out adesired industrial sequence or process and download the resultingprogram files to the controller 118. Separately, developers designvisualization screens and associated navigation structures for HMIs 114using an HMI development platform (e.g., executing on client device 122)and download the resulting visualization files to the HMI 114. Someindustrial devices 120—such as motor drives, telemetry devices, safetyinput devices, etc.—may also require configuration using separate deviceconfiguration tools (e.g., executing on client device 128) that arespecific to the device being configured. Such device configuration toolsmay be used to set device parameters or operating modes (e.g., high/lowlimits, output signal formats, scale factors, energy consumption modes,etc.).

The necessity of using separate configuration tools to program andconfigure disparate aspects of an industrial automation system resultsin a piecemeal design approach whereby different but related oroverlapping aspects of an automation system are designed, configured,and programmed separately on different development environments. Forexample, a motion control system may require an industrial controller tobe programmed and a control loop to be tuned using a control logicprogramming platform, a motor drive to be configured using anotherconfiguration platform, and an associated HMI to be programmed using avisualization development platform. Related peripheral systems—such asvision systems, safety systems, etc.—may also require configurationusing separate programming or development applications.

This segregated development approach can also necessitate considerabletesting and debugging efforts to ensure proper integration of theseparately configured system aspects. In this regard, intended datainterfacing or coordinated actions between the different system aspectsmay require significant debugging due to a failure to properlycoordinate disparate programming efforts.

Industrial development platforms are also limited in terms of thedevelopment interfaces offered to the user to facilitate programming andconfiguration. These interfaces typically offer a fixed user experiencethat requires the user to develop control code, visualizations, or othercontrol system aspects using a vendor-specific or industry-specificlanguage or interface.

To address at least some of these or other issues, one or moreembodiments described herein provide an integrated developmentenvironment (IDE) for programming and configuration of multiple aspectsof an industrial automation system using a common design environment anddata model. Embodiments of the industrial IDE can be used to configureand manage automation system devices in a common way, facilitatingintegrated, multi-discipline programming of control, visualization, andother aspects of the control system.

In general, the industrial IDE implements features that span the fullautomation lifecycle, including design (e.g., device selection andsizing, controller programming, visualization development, deviceconfiguration, testing, etc.); installation, configuration andcommissioning; operation, improvement, and administration; andtroubleshooting, expanding, and upgrading.

Embodiments of the industrial IDE can include a library of modular codeand visualizations that are specific to industry verticals and commonindustrial applications within those verticals. These code andvisualization modules can simplify development and shorten thedevelopment cycle, while also supporting consistency and reuse across anindustrial enterprise.

Also, one or more embodiments of the industrial IDE can supportdevelopment of control programming using an industrial domain-specificlanguage (DSL) that allows control programming to be written using ascripted programming language having features catered to the industrialdomain. For example, the industrial DSL can support the creation andinclusion of automation objects within the control program. Automationobject types can represent various types of industrial assets orentities, including but not limited to industrial processes, machines,industrial devices (e.g., controllers, motor drives, telemetry devices,etc.), industrial robots, actuators, HMI screens, control routines,controller tags, or other such entities specific to the industrialdomain. These automation objects can be organized according to anamespace that defines parent-child relationships between the objects;e.g., in terms of the hierarchical relationships between theirassociated industrial assets or entities.

The industrial DSL can simplify and streamline development of industrialcontrol code relative to using conventional graphics-based controlprogramming formats such as ladder logic, since a script-basedindustrial DSL can be used to write programming code using fewer mouseclicks relative to traditional control programming environments. Editingtools inherent to the industrial DSL can also provide dynamicprogramming feedback that guides the developer through the process ofdeveloping control code. This feedback can be generated based onindustry-specific or vertical-specific standards encoded in theindustrial IDE as programming guardrails. These guardrails can provideprogramming feedback that facilitate compliance with industry control orprogramming standards, which may be specific to the particularindustrial vertical for which the program is being developed (e.g.automotive, food and drug, textiles, oil and gas, etc.). The guardrailscan also be customized to provide feedback that keeps programmers withincompliance of in-house programming standards.

The industrial IDE can also provide tools that extend the platform tousers who wish to customize the industrial DSL to suit their preferredprogramming approaches. This can include allowing users to define theirown automation objects, programming syntax, syntax or errorhighlighting, programming guardrails, or other such features of theindustrial DSL.

FIG. 2 is a block diagram of an example integrated developmentenvironment (IDE) system 202 according to one or more embodiments ofthis disclosure. Aspects of the systems, apparatuses, or processesexplained in this disclosure can constitute machine-executablecomponents embodied within machine(s), e.g., embodied in one or morecomputer-readable mediums (or media) associated with one or moremachines. Such components, when executed by one or more machines, e.g.,computer(s), computing device(s), automation device(s), virtualmachine(s), etc., can cause the machine(s) to perform the operationsdescribed.

IDE system 202 can include a user interface component 204 including aDSL editor 224, a project generation component 206, a project deploymentcomponent 208, an editor definition component 210, one or moreprocessors 218, and memory 220. In various embodiments, one or more ofthe user interface component 204, project generation component 206,project deployment component 208, editor definition component 210, theone or more processors 218, and memory 220 can be electrically and/orcommunicatively coupled to one another to perform one or more of thefunctions of the IDE system 202. In some embodiments, components 204,206, 208, and 210 can comprise software instructions stored on memory220 and executed by processor(s) 218. IDE system 202 may also interactwith other hardware and/or software components not depicted in FIG. 2 .For example, processor(s) 218 may interact with one or more externaluser interface devices, such as a keyboard, a mouse, a display monitor,a touchscreen, or other such interface devices.

User interface component 204 can be configured to receive user input andto render output to the user in any suitable format (e.g., visual,audio, tactile, etc.). In some embodiments, user interface component 204can be configured to communicatively interface with an IDE client thatexecutes on a client device (e.g., a laptop computer, tablet computer,smart phone, etc.) that is communicatively connected to the IDE system202 (e.g., via a hardwired or wireless connection). The user interfacecomponent 204 can then receive user input data and render output datavia the IDE client. In other embodiments, user interface component 314can be configured to generate and serve suitable interface screens to aclient device (e.g., program development screens), and exchange data viathese interface screens. Input data that can be received via variousembodiments of user interface component 204 can include, but is notlimited to, programming code, industrial design specifications or goals,engineering drawings, AR/VR input, DSL definitions, video or image data,or other such input. Output data rendered by various embodiments of userinterface component 204 can include program code, programming feedback(e.g., error and highlighting, coding suggestions, etc.), programmingand visualization development screens, etc.

Project generation component 206 can be configured to create a systemproject comprising one or more project files based on design inputreceived via the user interface component 204, as well as industrialknowledge, predefined code modules, and automation objects 222maintained by the IDE system 202. Project deployment component 208 canbe configured to commission the system project created by the projectgeneration component to appropriate industrial devices (e.g.,controllers, HMI terminals, motor drives, AR/VR systems, etc.) forexecution. To this end, project deployment component 208 can identifythe appropriate target devices to which respective portions of thesystem project should be sent for execution, translate these respectiveportions to formats understandable by the target devices, and deploy thetranslated project components to their corresponding devices.

Editor definition component 210 can be configured to receive DSLdefinition data that defines or modifies programming aspects of theindustrial DSL, and to configure the DSL editor in accordance with theDSL definition data. DSL programming features that can be configured viathe editor definition component 210 can include, but are not limited to,the DSL syntax, types of programming feedback and conditions under whichthe feedback is provided (e.g., error highlighting, syntax highlighting,coding recommendations, etc.), available automation objects, namespacedefinitions, or other such features.

The one or more processors 218 can perform one or more of the functionsdescribed herein with reference to the systems and/or methods disclosed.Memory 220 can be a computer-readable storage medium storingcomputer-executable instructions and/or information for performing thefunctions described herein with reference to the systems and/or methodsdisclosed.

FIG. 3 is a diagram illustrating a generalized architecture of theindustrial IDE system 202 according to one or more embodiments.Industrial IDE system 202 can implement a common set of services andworkflows spanning not only design, but also commissioning, operation,and maintenance. In terms of design, the IDE system 202 can support notonly industrial controller programming and HMI development, but alsosizing and selection of system components, device/system configuration,AR/VR visualizations, and other features. The IDE system 202 can alsoinclude tools that simplify and automate commissioning of the resultingproject and assist with subsequent administration of the deployed systemduring runtime.

Embodiments of the IDE system 202 that are implemented on a cloudplatform also facilitate collaborative project development wherebymultiple developers 304 contribute design and programming input to acommon automation system project 302. Collaborative tools supported bythe IDE system can manage design contributions from the multiplecontributors and perform version control of the aggregate system project302 to ensure project consistency.

Based on design and programming input from one or more developers 304,IDE system 202 generates a system project 302 comprising one or moreproject files. The system project 302 encodes control programming; HMI,AR, and/or VR visualizations; device or sub-system configuration data(e.g., drive parameters, vision system configurations, telemetry deviceparameters, safety zone definitions, etc.); or other such aspects of anindustrial automation system being designed. IDE system 202 can identifythe appropriate target devices 306 on which respective aspects of thesystem project 302 should be executed (e.g., industrial controllers, HMIterminals, variable frequency drives, safety devices, etc.), translatethe system project 302 to executable files that can be executed on therespective target devices, and deploy the executable files to theircorresponding target devices 306 for execution, thereby commissioningthe system project 302 to the plant floor for implementation of theautomation project.

To support enhanced development capabilities, some embodiments of IDEsystem 202 can be built on an object-based data model rather than atag-based architecture. Automation objects 222 serve as the buildingblock for this object-based development architecture. FIG. 4 is adiagram illustrating several example automation object properties thatcan be leveraged by the IDE system 202 in connection with building,deploying, and executing a system project 302. Automation objects 222can be created and augmented during design, integrated into larger datamodels, and consumed during runtime. These automation objects 222provide a common data structure across the IDE system 202 and can bestored in an object library (e.g., part of memory 220) for reuse. Theobject library can store predefined automation objects 222 representingvarious classifications of real-world industrial assets 402, includingbut not limited to pumps, tanks, values, motors, motor drives (e.g.,variable frequency drives), industrial robots, actuators (e.g.,pneumatic or hydraulic actuators), or other such assets. Automationobjects 222 can represent elements at substantially any level of anindustrial enterprise, including individual devices, machines made up ofmany industrial devices and components (some of which may be associatedwith their own automation objects 222), and entire production lines orprocess control systems.

An automation object 222 for a given type of industrial asset can encodesuch aspects as 2D or 3D visualizations, alarms, control coding (e.g.,logic or other type of control programming), analytics, startupprocedures, testing protocols, validation reports, simulations,schematics, security protocols, and other such properties associatedwith the industrial asset 402 represented by the object 222. Automationobjects 222 can also be geotagged with location information identifyingthe location of the associated asset. During runtime of the systemproject 302, the automation object 222 corresponding to a givenreal-world asset 402 can also record status or operational history datafor the asset. In general, automation objects 222 serve as programmaticrepresentations of their corresponding industrial assets 402, and can beincorporated into a system project 302 as elements of control code, a 2Dor 3D visualization, a knowledgebase or maintenance guidance system forthe industrial assets, or other such aspects.

FIG. 5 is a diagram illustrating example data flows associated withcreation of a system project 302 for an automation system being designedusing IDE system 202 according to one or more embodiments. A clientdevice 504 (e.g., a laptop computer, tablet computer, desktop computer,mobile device, wearable AR/VR appliance, etc.) executing an IDE clientapplication 514 can access the IDE system's project development toolsand leverage these tools to create a comprehensive system project 302for an automation system being developed. Through interaction with thesystem's user interface component 204, developers can submit designinput 512 to the IDE system 202 in various supported formats, includingindustry-specific control programming (e.g., control logic, structuredtext, sequential function charts, etc.) and HMI screen configurationinput. Based on this design input 512 and information stored in anindustry knowledgebase (predefined code modules 508 and visualizations510, guardrail templates 506, physics-based rules 516, etc.), userinterface component 204 renders design feedback 518 designed to assistthe designer in connection with developing a system project 302 forconfiguration, control, and visualization of an industrial automationsystem.

In addition to control programming and visualization definitions, someembodiments of IDE system 202 can be configured to receive digitalengineering drawings (e.g., computer-aided design (CAD) files) as designinput 512. In such embodiments, project generation component 206 cangenerate portions of the system project 302—e.g., by automaticallygenerating control and/or visualization code—based on analysis ofexisting design drawings. Drawings that can be submitted as design input512 can include, but are not limited to, P&ID drawings, mechanicaldrawings, flow diagrams, or other such documents. For example, a P&IDdrawing can be imported into the IDE system 202, and project generationcomponent 206 can identify elements (e.g., tanks, pumps, etc.) andrelationships therebetween conveyed by the drawings. Project generationcomponent 206 can associate or map elements identified in the drawingswith appropriate automation objects 222 corresponding to these elements(e.g., tanks, pumps, etc.) and add these automation objects 222 to thesystem project 302. The device-specific and asset-specific automationobjects 222 include suitable code and visualizations to be associatedwith the elements identified in the drawings. In general, the IDE system202 can examine one or more different types of drawings (mechanical,electrical, piping, etc.) to determine relationships between devices,machines, and/or assets (including identifying common elements betweenthe drawings) and intelligently associate these elements withappropriate automation objects 222, code modules 508, and visualizations510. The IDE system 202 can leverage physics-based rules 516 as well aspre-defined code modules 508 and visualizations 510 as necessary inconnection with generating code or project data for system project 302.

The IDE system 202 can also determine whether pre-defined visualizationcontent is available for any of the objects discovered in the drawingsand generate appropriate HMI screens or AR/VR content for the discoveredobjects based on these pre-defined visualizations. To this end, the IDEsystem 202 can store industry-specific, asset-specific, and/orapplication-specific visualizations 510 that can be accessed by theproject generation component 206 as needed. These visualizations 510 canbe classified according to industry or industrial vertical (e.g.,automotive, food and drug, oil and gas, pharmaceutical, etc.), type ofindustrial asset (e.g., a type of machine or industrial device), a typeof industrial application (e.g., batch processing, flow control, webtension control, sheet metal stamping, water treatment, etc.), or othersuch categories. Predefined visualizations 510 can comprisevisualizations in a variety of formats, including but not limited to HMIscreens or windows, mashups that aggregate data from multiplepre-specified sources, AR overlays, VR objects representing 3Dvirtualizations of the associated industrial asset, or other suchvisualization formats. IDE system 202 can select a suitablevisualization for a given object based on a predefined associationbetween the object type and the visualization content.

In another example, markings applied to an engineering drawing by a usercan be understood by some embodiments of the project generationcomponent 206 to convey a specific design intention or parameter. Forexample, a marking in red pen can be understood to indicate a safetyzone, two circles connected by a dashed line can be interpreted as agearing relationship, and a bold line may indicate a cammingrelationship. In this way, a designer can sketch out design goals on anexisting drawing in a manner that can be understood and leveraged by theIDE system 202 to generate code and visualizations. In another example,the project generation component 206 can learn permissives andinterlocks (e.g., valves and their associated states) that serve asnecessary preconditions for starting a machine based on analysis of theuser's CAD drawings. Project generation component 206 can generate anysuitable code (ladder, function blocks, etc.), device configurations,and visualizations based on analysis of these drawings and markings forincorporation into system project 302. In some embodiments, userinterface component 204 can include design tools for developingengineering drawings within the IDE platform itself, and the projectgeneration component 206 can generate this code as a background processas the user is creating the drawings for a new project. In someembodiments, project generation component 206 can also translate statemachine drawings to a corresponding programming sequence, yielding atleast skeletal code that can be enhanced by the developer withadditional programming details as needed.

Also, or in addition, some embodiments of IDE system 202 can supportgoal-based automated programming. For example, the user interfacecomponent 204 can allow the user to specify production goals for asystem being designed (e.g., specifying that a bottling plant beingdesigned must be capable of producing at least 5000 bottles per secondduring normal operation) and any other relevant design constraintsapplied to the design project (e.g., budget limitations, available floorspace, available control cabinet space, etc.). Based on thisinformation, the project generation component 206 will generate portionsof the system project 302 to satisfy the specified design goals andconstraints. Portions of the system project 302 that can be generated inthis manner can include, but are not limited to, device and equipmentselections (e.g., definitions of how many pumps, controllers, stations,conveyors, drives, or other assets will be needed), associated deviceconfigurations (e.g., tuning parameters, network settings, driveparameters, etc.), control coding, or HMI screens suitable forvisualizing the automation system being designed.

Some embodiments of project generation component 206 can also monitorcustomer-specific design approaches for commonly programmed functions(e.g., pumping applications, batch processes, etc.) and generaterecommendations for design modules (e.g., code modules 508,visualizations 510, etc.) that the user may wish to incorporate into acurrent design project based on an inference of the designer's goals andlearned approaches to achieving the goal. For example, given a set ofindustrial equipment being programmed, user interface component 204 canrender recommended development steps or code modules 508 the designermay wish to use based on how the designer typically configures andprograms this equipment.

In some embodiments, IDE system 202 can also store and implementguardrail templates 506 that define design guardrails intended to ensurethe project's compliance with internal or external design standards.Based on design parameters defined by one or more selected guardrailtemplates 506, user interface component 204 can provide, as a subset ofdesign feedback 518, dynamic recommendations or other types of feedbackduring project development designed to keep the developer's systemproject 302 within compliance of internal or external requirements orstandards (e.g., certifications such as TUV certification, in-housedesign standards, industry-specific or vertical-specific designstandards, etc.). This feedback 518 can take the form of text-basedrecommendations (e.g., recommendations to rewrite an indicated portionof control code to comply with a defined programming standard), syntaxhighlighting, error highlighting, auto-completion of code snippets, orother such formats. In this way, IDE system 202 can customize designfeedback 518—including programming recommendations, recommendations ofpredefined code modules 508 or visualizations 510, the types and formatof error and syntax highlighting, etc.—in accordance with the type ofindustrial system being developed and any applicable in-house designstandards.

Guardrail templates 506 can also be designed to maintain compliance withglobal best practices applicable to control programming or other aspectsof project development. For example, user interface component 204 maygenerate and render an alert if a developer's control programing isdeemed to be too complex as defined by criteria specified by one or moreguardrail templates 506. Since different verticals (e.g., automotive,pharmaceutical, oil and gas, food and drug, marine, etc.) must adhere todifferent standards and certifications, the IDE system 202 can maintaina library of guardrail templates 506 for different internal and externalstandards and certifications, including customized user-specificguardrail templates 506. These guardrail templates 506 can be classifiedaccording to industrial vertical, type of industrial application, plantfacility (in the case of custom in-house guardrail templates 506) orother such categories. During development, project generation component206 can select and apply a subset of guardrail templates 506 determinedto be relevant to the project currently being developed, based on adetermination of such aspects as the industrial vertical to which theproject relates, the type of industrial application being programmed(e.g., flow control, web tension control, a certain batch process,etc.), or other such aspects. Project generation component 206 canleverage guardrail templates 506 to implement rules-based programming,whereby programming feedback such as dynamic intelligent autocorrection,type-aheads, or coding suggestions are rendered based on industryexpertise and best practices (e.g., identifying inefficiencies in codebeing developed and recommending appropriate corrections).

Users can also run their own internal guardrail templates 506 againstcode provided by outside vendors (e.g., OEMs) to ensure that this codecomplies with in-house programming standards. In such scenarios,vendor-provided code can be submitted to the IDE system 202, and userinterface component 204 can analyze this code in view of in-house codingstandards specified by one or more custom guardrail templates 506. Basedon results of this analysis, user interface component 204 can indicateportions of the vendor-provided code (e.g., using highlights, overlaidtext, etc.) that do not conform to the programming standards set forthby the guardrail templates 506, and display suggestions for modifyingthe code in order to bring the code into compliance. As an alternativeor in addition to recommending these modifications, some embodiments ofproject generation component 206 can be configured to automaticallymodify the code in accordance with the recommendations to bring the codeinto conformance.

In making coding suggestions, project generation component 206 caninvoke selected code modules 508 stored in a code module database (e.g.,on memory 220). These code modules 508 comprise standardized codingsegments for common industrial tasks or applications (e.g., palletizing,flow control, web tension control, pick-and-place applications, etc.).In some embodiments, code modules 508 can be categorized according toone or more of an industrial vertical (e.g., automotive, food and drug,oil and gas, textiles, marine, pharmaceutical, etc.), an industrialapplication, or a type of machine or device to which the code module 508is applicable. In some embodiments, project generation component 206 caninfer a programmer's current programming task or design goal based onprogrammatic input being provided by a the programmer, and determine,based on this task or goal, whether one of the pre-defined code modules508 may be appropriately added to the control program being developed toachieve the inferred task or goal. For example, project generationcomponent 206 may infer that the programmer is currently developingcontrol code for transferring material from a first tank to anothertank, and in response, recommend inclusion of a predefined code module508 comprising standardized code for controlling the valves, pumps, orother assets necessary to achieve the material transfer.

Customized guardrail templates 506 can also be defined to capture thenuances of a customer site that should be taken into consideration inthe project design. For example, a guardrail template 506 could recordthe fact that the automation system being designed will be installed ina region where power outages are common, and will factor thisconsideration when generating design feedback 518; e.g., by recommendingimplementation of backup uninterruptable power supplies and suggestinghow these should be incorporated, as well as recommending associatedprogramming or control strategies that take these outages into account.

IDE system 202 can also use guardrail templates 506 to guide userselection of equipment or devices for a given design goal; e.g., basedon the industrial vertical, type of control application (e.g., sheetmetal stamping, die casting, palletization, conveyor control, webtension control, batch processing, etc.), budgetary constraints for theproject, physical constraints at the installation site (e.g., availablefloor, wall or cabinet space; dimensions of the installation space;etc.), equipment already existing at the site, etc. Some or all of theseparameters and constraints can be provided as design input 512, and userinterface component 204 can render the equipment recommendations as asubset of design feedback 518. In some embodiments, project generationcomponent 206 can also determine whether some or all existing equipmentcan be repurposed for the new control system being designed. Forexample, if a new bottling line is to be added to a production area,there may be an opportunity to leverage existing equipment since somebottling lines already exist. The decision as to which devices andequipment can be reused will affect the design of the new controlsystem. Accordingly, some of the design input 512 provided to the IDEsystem 202 can include specifics of the customer's existing systemswithin or near the installation site. In some embodiments, projectgeneration component 206 can apply artificial intelligence (AI) ortraditional analytic approaches to this information to determine whetherexisting equipment specified in design in put 512 can be repurposed orleveraged. Based on results of this analysis, project generationcomponent 206 can generate, as design feedback 518, a list of any newequipment that may need to be purchased based on these decisions.

In some embodiments, IDE system 202 can offer design recommendationsbased on an understanding of the physical environment within which theautomation system being designed will be installed. To this end,information regarding the physical environment can be submitted to theIDE system 202 (as part of design input 512) in the form of 2D or 3Dimages or video of the plant environment. This environmental informationcan also be obtained from an existing digital twin of the plant, or byanalysis of scanned environmental data obtained by a wearable ARappliance in some embodiments. Project generation component 206 cananalyze this image, video, or digital twin data to identify physicalelements within the installation area (e.g., walls, girders, safetyfences, existing machines and devices, etc.) and physical relationshipsbetween these elements. This can include ascertaining distances betweenmachines, lengths of piping runs, locations and distances of wiringharnesses or cable trays, etc. Based on results of this analysis,project generation component 206 can add context to schematics generatedas part of system project 302, generate recommendations regardingoptimal locations for devices or machines (e.g., recommending a minimumseparation between power and data cables), or make other refinements tothe system project 302. At least some of this design data can begenerated based on physics-based rules 516, which can be referenced byproject generation component 206 to determine such physical designspecifications as minimum safe distances from hazardous equipment (whichmay also factor into determining suitable locations for installation ofsafety devices relative to this equipment, given expected human orvehicle reaction times defined by the physics-based rules 516), materialselections capable of withstanding expected loads, piping configurationsand tuning for a given flow control application, wiring gauges suitablefor an expected electrical load, minimum distances between signal wiringand electromagnetic field (EMF) sources to ensure negligible electricalinterference, or other such design features that are dependent onphysical rules.

In an example use case, relative locations of machines and devicesspecified by physical environment information submitted to the IDEsystem 202 can be used by the project generation component 206 togenerate design data for an industrial safety system. For example,project generation component 206 can analyze distance measurementsbetween safety equipment and hazardous machines and, based on thesemeasurements, determine suitable placements and configurations of safetydevices and associated safety controllers that ensure the machine willshut down within a sufficient safety reaction time to prevent injury(e.g., in the event that a person runs through a light curtain).

In some embodiments, project generation component 206 can also analyzephotographic or video data of an existing machine to determine inlinemechanical properties such as gearing or camming and factor thisinformation into one or more guardrail templates 506 or designrecommendations.

In some embodiments, user interface component 204 is associated with adomain-specific language (DSL) editor 224 that can allow users toprogram their own development interfaces for interacting with the IDEsystem 202 and populating the system project 302, as will be discussedin more detail below.

As noted above, the system project 302 generated by IDE system 202 for agiven automaton system being designed can be built upon an object-basedarchitecture that uses automation objects 222 as building blocks. FIG. 6is a diagram illustrating an example system project 302 thatincorporates automation objects 222 into the project model. In thisexample, various automation objects 222 representing analogousindustrial devices, systems, or assets of an automation system (e.g., aprocess, tanks, valves, pumps, etc.) have been incorporated into systemproject 302 as elements of a larger project data model 602. The projectdata model 602 also defines hierarchical relationships between theseautomation objects 222. According to an example relationship, a processautomation object representing a batch process may be defined as aparent object to a number of child objects representing devices andequipment that carry out the process, such as tanks, pumps, and valves.Each automation object 222 has associated therewith object properties orattributes specific to its corresponding industrial asset (e.g., thosediscussed above in connection with FIG. 4 ), including executablecontrol programming for controlling the asset (or for coordinating theactions of the asset with other industrial assets) and visualizationsthat can be used to render relevant information about the asset duringruntime.

At least some of the attributes of each automation object 222 aredefault properties defined by the IDE system 202 based on encodedindustry expertise pertaining to the asset represented by the objects.Other properties can be modified or added by the developer as needed(via design input 512) to customize the object 222 for the particularasset and/or industrial application for which the system projects 302 isbeing developed. This can include, for example, associating customizedcontrol code, HMI screens, AR presentations, or help files associatedwith selected automation objects 222. In this way, automation objects222 can be created and augmented as needed during design for consumptionor execution by target control devices during runtime.

Once development on a system project 302 has been completed,commissioning tools supported by the IDE system 202 can simplify theprocess of commissioning the project in the field. When the systemproject 302 for a given automation system has been completed, the systemproject 302 can be deployed to one or more target control devices forexecution. FIG. 7 is a diagram illustrating commissioning of a systemproject 302. Project deployment component 208 can compile or otherwisetranslate a completed system project 302 into one or more executablefiles or configuration files that can be stored and executed onrespective target industrial devices of the automation system (e.g.,industrial controllers 118, HMI terminals 114 or other types ofvisualization systems, motor drives 710, telemetry devices, visionsystems, safety relays, etc.).

Conventional control program development platforms require the developerto specify the type of industrial controller (e.g., the controller'smodel number) on which the control program will run prior todevelopment, thereby binding the control programming to a specifiedcontroller. Controller-specific guardrails are then enforced duringprogram development which limit how the program is developed given thecapabilities of the selected controller. By contrast, some embodimentsof the IDE system 202 can abstract project development from the specificcontroller type, allowing the designer to develop the system project 302as a logical representation of the automation system in a manner that isagnostic to where and how the various control aspects of system project302 will run. Once project development is complete and system project302 is ready for commissioning, the user can specify (via user interfacecomponent 204) target devices on which respective aspects of the systemproject 302 are to be executed. In response, an allocation engine of theproject deployment component 208 will translate aspects of the systemproject 302 to respective executable files formatted for storage andexecution on their respective target devices.

For example, system project 302 may include—among other projectaspects—control code, visualization screen definitions, and motor driveparameter definitions. Upon completion of project development, a usercan identify which target devices—including an industrial controller118, an HMI terminal 114, and a motor drive 710—are to execute orreceive these respective aspects of the system project 302. Projectdeployment component 208 can then translate the controller code definedby the system project 302 to a control program file 702 formatted forexecution on the specified industrial controller 118 and send thiscontrol program file 702 to the controller 118 (e.g., via plant network116). Similarly, project deployment component 208 can translate thevisualization definitions and motor drive parameter definitions to avisualization application 704 and a device configuration file 708,respectively, and deploy these files to their respective target devicesfor execution and/or device configuration. In general, projectdeployment component 208 performs any conversions necessary to allowaspects of system project 302 to execute on the specified devices. Anyinherent relationships, handshakes, or data sharing defined in thesystem project 302 are maintained regardless of how the various elementsof the system project 302 are distributed. In this way, embodiments ofthe IDE system 202 can decouple the project from how and where theproject is to be run. This also allows the same system project 302 to becommissioned at different plant facilities having different sets ofcontrol equipment. That is, some embodiments of the IDE system 202 canallocate project code to different target devices as a function of theparticular devices found on-site. IDE system 202 can also allow someportions of the project file to be commissioned as an emulator or on acloud-based controller.

As an alternative to having the user specify the target control devicesto which the system project 302 is to be deployed, some embodiments ofIDE system 202 can actively connect to the plant network 116 anddiscover available devices, ascertain the control hardware architecturepresent on the plant floor, infer appropriate target devices forrespective executable aspects of system project 302, and deploy thesystem project 302 to these selected target devices. As part of thiscommissioning process, IDE system 202 can also connect to remoteknowledgebases (e.g., web-based or cloud-based knowledgebases) todetermine which discovered devices are out of date or require firmwareupgrade to properly execute the system project 302. In this way, the IDEsystem 202 can serve as a link between device vendors and a customer'splant ecosystem via a trusted connection in the cloud.

Copies of system project 302 can be propagated to multiple plantfacilities having varying equipment configurations using smartpropagation, whereby the project deployment component 208 intelligentlyassociates project components with the correct industrial asset orcontrol device even if the equipment on-site does not perfectly matchthe defined target (e.g., varying pump types at different sites). Fortarget devices that do not perfectly match the expected asset, projectdeployment component 208 can calculate the estimated impact of runningthe system project 302 on non-optimal target equipment and generatewarnings or recommendations for mitigating expected deviations fromoptimal project execution.

Returning briefly to FIG. 5 , as an alternative to entering controlprogramming in a graphical industry-standard format such as ladder logic(as a portion of design input 512), some embodiments of user interfacecomponent 204 can support entry of control programming as a scripted,text-based syntax. In some such embodiments, the scripted language maybe a domain-specific language (DSL) customized for industrial controlprogramming. FIG. 8 is a diagram illustrating control programming usingan industrial DSL and compilation of the DSL programming to yieldexecutable industrial code 806. According to these embodiments, userinterface component 204 is associated with a DSL editor 224 that rendersa DSL programming interface for entry of industrial DSL script 802. TheDSL editor 224 also supports associated editor tools 804 that providedynamic assistance during programming. Writing control code using atext-based DSL syntax—allowing programming objects to be describedthrough text—can be preferable to programming with ladder logic or othergraphical programming platforms typically used to program automationsystems, since experienced programmers can generate code more quicklyusing text-based programming syntax and associated editor tools 804 thatrequire fewer mouse clicks. Editor tools 804 supported by the DSL editor224 can include, but are not limited to, error highlighting, syntaxhighlighting, code snippet management, type-ahead or autocompletefunctionality, intelligent programming suggestions, and other suchtools. Some or all of these programming services can be provided by alanguage server 808 associated with the DSL editor 224.

In some embodiments, the industrial DSL can reference a logical modeldefining a hierarchical organization of automation objects, which servesas a namespace for the automation objects and the elements containedwithin the automation objects. FIG. 9 a is an example hierarchicalautomation object namespace 902 that can be supported by someembodiments of the industrial DSL. This example hierarchical structureof automation objects may comprise a plant level, an area level, a linelevel, a machine level, and a device level. Under this namespace, anautomation object representing a particular tank of a mixing linelocated within a batching area of a plant can be referenced using thefollowing example name scope: myFactory.batchingArea.mixingLine.tank101(assuming types formatted using the camel case naming convention). Ingeneral, each automation object 222 within the hierarchy defines aunique name scope, which is the union of the object's name plus thenames of its parent automation objects.

In addition to automation objects 222 representing devices (e.g.,industrial controllers, drives, HMI terminals, optical safety devices,etc.), machines, production areas, or other industrial assets, IDEsystem 202 can also support automation objects 222 representing elementsof a control program, including but not limited to the program itself aswell as add-on instructions, data tags, ladder logic routines or rungs,or other such programmatic elements within the program. For example, acontrol program that facilitates control of a tank (tank101) within aspecified production area (Area1) may be referenced within the DSLnamespace as Area1.tank101.tankProgram.

Similarly, automation objects 222 can be defined that representvisualizations elements, such as HMI screens, pop-up windows, augmentedreality overlays, etc. Such visualization automation objects 222 can bebound to a parent automaton object 222 representing the industrial assetwith which the visualization is to be associated. For example, a screenautomation object 222 representing an HMI screen for visualizing a tankcan be defined within the DSL namespace as a child object of the tank's(parent) automation object. The HMI screen automation object 222 can bewritten to define the dimensions, colors (e.g., background color, fontcolor, etc.), text, or other such properties of the screen.

Any type of application that can be deployed to an industrialdevice—e.g., control programs, HMI applications, motor driveapplications, batch control applications, etc.—can be associated withits own automation object 222 defined within the DSL namespace and boundto its appropriate parent automation object (representing the targetdevice or asset on which the application will run). In some embodiments,elements within an application—e.g., tags, rungs, routines, tasks, HMIgraphical elements, etc.—can be referenced using a different namespacethan that used for physical industrial assets, or using a nestednamespace within the greater asset namespace. For example, FIG. 9 b isanother example automation object namespace hierarchy 904 for controlapplication elements, which can be supported by some embodiments of thenamespace DSL. This example control application namespace comprises acontrol device level, a task level, a program level, and a tag level.Under this namespace, an automation object representing a tag (e.g.,tagA) defined in a control program can be referenced using the followingexample name scope: myController1.mainTask.mainProgram.tagA. Theapplication namespace 04 can be nested within the asset namespace 902 insome embodiments, such that automation objects 222 for an applicationelement defined in namespace 904 can be associated with a device definedin namespace 902.

Automation objects 222 can also represent other elements of a controlsystem or industrial environment, such as control loops, safety zones,lot traceability systems, or other such elements.

Some or all of these automation objects 222 can be defined by thelogical model associated with the industrial DSL and can therefore bereferenced via the DSL's hierarchical namespace. DSL editor 224 can alsoallow users to define custom automation objects 222 and incorporatethese custom objects 222 into the editor's logical model (e.g., atspecified locations within the namespace hierarchy).

A given automation object definition can define the inputs, logic (e.g.,inline logic definitions or externally specified logic), outputs, andany of the properties or attributes described above in connection withFIG. 4 . These properties and attributes may be specified inline or maybe linked to the automation object via a scripted link to an externalsource (e.g. a support document for an industrial asset represented bythe automation object). These object definitions can be written andcalled within the industrial DSL editor 224.

In addition to intrinsic data types such as integers, double integers,Boolean, floating point, etc., DSL editor 224 can also supportdefinition of data types specific to industrial automation applications,including but not limited to screens (representing HMI screens), add-ongraphics, automation objects, devices (e.g., automation devices such ascontrollers, drives, telemetry devices, etc.), projects, models,applications (e.g., applications that can be deployed to a device forexecution, such as control logic, analytics applications, powermonitoring applications, etc.), programs, parameter connections, tasks,tags (e.g., controller tags), or other such data types. The DSL editor224 allows instances of these types to be created for inclusion in asystem project 302. Instances of each type may have certain propertiesor members that are a function of the type.

The industrial DSL supported by the DSL editor 224 can provideprogrammatic guardrails based on known relationships between industrialentities represented by automation objects (e.g., controllers, tags,HMIs, motor drives, tanks, valves, etc.), and editor tools 804 can guidethe project development workflow based on these known relationships.This can include, for example, identifying when a parent automationobject 222 (e.g., a tank automation object) has been invoked within theDSL program and rendering possible child automation objects 222 (e.g.,valves, pumps, etc.) associated with the parent object that the user maywish to reference.

DSL editor 224 allows a user to program any aspects of the systemproject 302 using a customizable industrial DSL script 802. The DSLeditor's parser 812 can then parse this DSL script 802 to yield ahierarchical model (e.g., an abstract syntax tree or another modelformat) of the program. The DSL editor's compiler 810 can then translatethis hierarchical model to industrial code 806 (including any automationobjects 222 defined by the DSL script 802) that is understandable andexecutable by an industrial control device (e.g., a programmable logiccontroller or another type of industrial control device). The resultingindustrial code 806 can then be added to system project 302 or deployeddirectly to the target control device. In general, the DSL editor 224can map the industrial DSL to a structured language understandable bythe target industrial control equipment.

In some embodiments, IDE system 202 can include application programminginterfaces (APIs) that allow third parties—such as OEMs, systemintegrators, industrial asset owners, or other such users—to programtheir own development interfaces and customize their own DSLs forinteracting with the IDE system's development platform and populating asystem project 302. FIG. 10 is a diagram illustrating customization ofthe IDE system's programming interface according to one or moreembodiments. In this example, the user interface component 204 and DSLeditor 224 can be associated with an editor definition component 210that can modify the DSL editor's programming interfaces based on DSLdefinitions 1002 submitted by a user. The editor definition component210 allows the user to define or modify the syntax of the industrial DSLsupported by the DSL editor 224, define objects (e.g., automationobjects) to be included in the DSL's logical model as well asrelationships between these objects, define one or more of the editortools 804 for guiding the developer through the programming workflow, ordefine other such features of the programming interface. Editordefinition component 210 can update the DSL editor 224 based on theseDSL definitions 1002 to thereby customize the IDE's developmentinterface in accordance with user requirements or preferences. In thisway, the industrial DSL can be used to extend the IDE platform tothird-party users, allowing users to define their own language scriptthat can be translated and compiled into industrial code 806 that can beexecuted on industrial equipment. By allowing users to define the syntaxand editor tools 804 (error highlights, syntax highlighting, automatedrecommendation, guardrails, etc.), the look and feel of the DSL editor'sinterface for generating industrial control code can be customized byend users.

FIG. 11 is a block diagram illustrating components of an example editordefinition component 210 according to one or more embodiments. In anexample implementation, a software development kit (SDK) 1102 and/orassociated libraries 1104 can be licensed that allow users (e.g., OEMsor system integrators) to build their own DSL editor 224, buildextensions, access the logical model, and add to system projects 302.The APIs 1106 can allow users to create their own language script as acustomized industrial DSL, which can then be parsed and compiled (e.g.,by parser 812 and compiler 810 of the DSL editor 224) to executablecontrol code that is understandable and executable by industrial controldevices. A translator 1108 between the APIs 1106 and the IDE developmentplatform can expose the system project 302 and allow users to writetheir own control code and customize the DSL editor 224.

In some embodiments, the IDE system 202 can also allow a user to installa plug-in for a known programming language—such as Python, C, structuredtext, etc.—and allow the user to develop industrial code in thislanguage. In such scenarios, the plug-in can map the selectedprogramming language to control code understandable and executable byindustrial controllers, HMIs, or other industrial devices. In this way,the DSL editor 224 allows the user to develop industrial control code ina preferred programming language, and can compile the customer's codeinto a form that the IDE system 202—and an industrial control device—canunderstand.

In some embodiments, IDE system 202 can support control programdevelopment using graphical industrial programming languages such asladder logic, function block diagrams, sequential function charts, orother such graphical languages. In such embodiments, the editordefinition component 210 can allow users to customize the graphicaldevelopment environment according to their preferences. This can includealtering the native nomenclature of the program editor to preferrednomenclature preferred by the user. For example, in the case of a ladderlogic development environment, DSL definitions 1002 submitted by theuser can include nomenclature mapping definitions that map the ladderlogic editor's native nomenclature to preferred nomenclature specifiedby the user. In an example scenario, the function for moving a datavalue from a source register to a destination register may be referredto as a MOV command in the editor's native nomenclature. To add thisfunctionality to a control program, users must select and add a MOVfunction block to a rung output of their ladder logic program. Since thename of this function block may be considered ambiguous to someprogrammers, a user may wish to change the name of this function blockto MOVE to more explicitly convey the function associated with thiscommand. Accordingly, the editor definition component 210 can allow theuser to change the name of this command from MOV to MOVE by submittingDSL definitions 1002 that define this nomenclature mapping. Once thismapping has been defined, all instances of the MOV command will belabeled MOVE within the ladder logic editing environment. Other aspectsof the ladder logic editor, including but not limited to text or rungcolors, function block dimensions or sizes, locations and visibility oftoolbars, or other such features can also be customized in this manner.

Since the IDE system 202 can support development of control programmingusing either a text-based syntax or a graphical format such as ladderlogic, the user interface component 204 of some embodiments of the IDEsystem 202 can be configured to render a control program underdevelopment in both formats simultaneously using two separate,simultaneously displayed editing windows. FIG. 12 is a diagramrepresenting the relationship between a graphical version 1202 of anindustrial control program (where the graphical format is ladder logicin the illustrated example) and a corresponding text version 1204 of theprogram. Both views of the control program can be generated based on theproject model 602 for the control program. The text version 1204 of theprogram comprises lines of alphanumeric text, each line of the textversion 1204 corresponding to a ladder logic rung of the graphicalversion 1202 version of the control program. Each line of text in thetext version 1204 defines the types of program elements contained in thecorresponding rung (e.g., normally open or normally closed contacts,output coils, timers, counters, instruction blocks, etc.), addressesassigned to the program elements (e.g., I/O addresses or internaladdresses), values of variables or parameters defined for programelements (e.g., timer preset values, counter preset values, etc.), orother such program elements. In the example text format depicted in FIG.12 , unique text labels are used to identify types of program elements(e.g., XIC, XIO, TON, etc.), and logical conditions (e.g., AND and ORoperations, which are represented as serial or parallel arrangements ofprogram elements in the ladder logic version) are defined using commas,spaces, and brackets. Parameter values and addresses assigned to a givenprogram element are defined within parentheses associated with theelement. Information in the text version 1204 is translatable to yieldthe ladder logic format depicted in the graphical version 1202, and viceversa. It is to be appreciated that the format of text version 1204depicted in FIG. 12 is only intended to be exemplary, and that othertext-based programming formats are within the scope of one or moreembodiments.

FIG. 13 is an example development interface 1302 that can be rendered bythe user interface component 204 for development of industrial controlprograms according to one or more embodiments. This example developmentinterface 1302 comprises two editor windows 1304 and 1306 for viewingthe same industrial control program in respective two formats—in a textformat (text editor window 1304) and in a graphical format such asladder logic (graphical editor window 1306). Development interface 1302also includes an explorer window 1308 for selectively navigating aspectsof the system project currently being viewed.

Users can submit design input 512 in the form of control programminginput via interaction with either of the editor windows 1304 or 1306.Program edits entered in one of the two windows 1304 or 1306, in theformat supported by that window, will be reflected in the other windowin that window's native format. That is, when a user submits a programedit in the form of text-based syntax via interaction with text editorwindow 1304, the project model 602 is updated accordingly, andconsequently the corresponding portion of the ladder logic program willalso be updated in the graphical editor window 1306 to reflect the editsubmitted to the text version of the program. Likewise, program editssubmitted as ladder logic modifications via graphical editor window 1306cause the project model 602 to be updated accordingly, which also causesthe view of the text-based version of the program to be updated in texteditor window 1304 to reflect the modifications. These cross-updatesbetween the text version 1204 and graphical version 1202 of a programare implemented by the user interface component 204 automatically whenthe user submits an edit via either of the two windows 1304 or 1306, anddo not require the updated program to be manually exported from one ofthe formats and imported into the other.

This arrangement of the development interface 1302 affords a user theoption to edit a control program in either format as desired and to seethese changes reflected in the other format without navigating to adifferent development interface view. In this regard, the user may findthat certain types of program edits—or edits to a project having a highdegree of complexity—are more easily entered as text-based syntaxsubmitted to the text version 1204 of the program via text editor window1304, while other types of edits are more easily submitted as graphicalladder logic edits via graphical editor window 1306.

Simultaneous rendering of a control program in both a text-based formatand a graphical format such as ladder logic can also aid introubleshooting while viewing an online version of the control programthat has been deployed to an industrial controller for execution. Insuch scenarios, the graphical editor window 1306 can animate the ladderlogic view of the program to convey the states of the program's ladderlogic rungs and program elements based on real-time data read from thecontroller. This can include, for example, highlighting the TRUE orFALSE states of ladder logic rung segments and their correspondingprogram elements, displaying the current digital and analog values ofdata tags associated with the program elements, or other suchanimations. These graphical animations rendered in the graphical editorwindow 1306 can assist the user in troubleshooting the control program.If the user determines that modifications to the control program arerequired based on this troubleshooting, these edits can be submitted, ifdesired, to the text version of the program rendered in the text editorwindow 1304 and synchronized to the industrial controller. These editswill also be reflected in the ladder logic view of the program renderedin graphical editor window 1306.

Also, in some embodiments, the editor windows 1304 and 1306 can benavigationally linked, such that the portion of the control program thatis currently visible in one of the two editor windows 1304 and 1306matches the corresponding portion of the program currently visible inthe other window. By this configuration, if a user navigates to aselected section of a control program in one of the windows 1304 or1306, the user interface component 204 automatically updates the viewrendered in the other window so that the same portions of the program(e.g., the same routines, the same lines of code, etc.) are renderedsimultaneously in the two windows 1304 and 1306. In some embodiments,the development interface 1302 can allow the user to selectively enableor disable this automated navigational mirroring of the two viewsafforded by windows 1304 and 1306. Disabling the navigational mirroringmay be appropriate, for example, in scenarios in which the user wishesto visually reference a first section of a control program in either thetext format or the graphical format, while viewing and editing adifferent section in the other format.

As noted above, the IDE system's editor definition component 210 canallow users to submit DSL definitions 1002 to customize either of thetext-based syntax of the plain text format or the graphicalcharacteristics of the graphical format used to develop controlprograms. Some of these DSL definitions 1002 may be specific to only oneof the two programming formats. For example, some DSL definitions 1002may define customized syntax highlighting, type-ahead recommendations,or other such customizations that are applicable only to the textversion 1204 of the program displayed in text editor window 1304. OtherDSL definitions 1002 may define customizations to rung highlight colors,rung highlight conditions, rung spacings, or other such customizationsthat are only applicable only to the graphical version 1202.

Still other DSL definitions 1002 may define customizations that areapplicable to both control programming formats. For example, DSLdefinitions 1002 that define customized automation objects 222 that areto be made available as part of the logical model, as well as anyrelationships between these automation objects, are applicable to boththe text version 1202 and the graphical version 1204 of the program,since the customized automation objects 222 can be invoked and added tothe program in either format using appropriate calls to the automationobjects 222.

An automation object 222 added to a control program via either of thetwo development windows 1304 or 1306 will be added to and displayed inboth versions 1202 and 1204 of the program. In the text editor window1304 the automation object 222 may be formatted as a text string thatidentifies the name of the object and any user-defined values assignedto the object's respective properties. In some embodiments, entering thename of an automation object 222 in a line of the text-formatted programin the text editor window 1304 can cause the text editor toauto-complete a text-based template for the automation object 222 thatincludes generic placeholders for values of the object's properties (asdefined by the DSL definitions 1002 in the case of custom automationobjects 222), which the user can then replace with user-defined valuesfor those properties. In the graphical editor window 1306 an automationobject 222 can be formatted as an instruction block that can be placedon a rung of the ladder logic program, as a function block of a functionblock diagram, or as another type of graphical representation.Automation objects 222 added to either version of the control programwill accord to the namespace hierarchies defined in the logical model,as described above in connection with FIGS. 9 a and 9 b.

As noted above, some embodiments of the IDE system 202 can allow a userto install a plug-in for a common text-based programming language suchas Python, C, structured text, or another known language. This plug-incan allow a user to develop control programs using this common languageby mapping the selected text-based language to executable control code.In such embodiments, the development interface 1302 can render a controlprogram in the selected text-based format in the text editor window 1304while simultaneously rendering the control program in the correspondinggraphical format in the graphical editor window 1306. The plug-in canmap elements of the selected text-based programming language tocorresponding elements of the graphical format (e.g., by mapping thetext-based language to elements of the project model 602 referenced byboth formats) such that program edits entered in either the text formator the graphical format are automatically reflected in the other of thetwo formats.

By rendering a control program under development in both plain text andgraphical formats simultaneously on the same development interface,embodiments of the IDE system 202 can improve the workflow of controlprogram development by allowing the user to easily alternate betweenboth formats as needed while editing or troubleshooting the program, andto instantly see changes made in one format reflected in the otherformat.

As noted above, some embodiments of IDE system 202 can be embodied on acloud platform. FIG. 14 is a diagram illustrating an examplearchitecture in which cloud-based IDE services 1402 are used to developand deploy industrial applications to a plant environment. In thisexample, the industrial environment includes one or more industrialcontrollers 118, HMI terminals 114, motor drives 710, servers 1401running higher level applications (e.g., ERP, MES, etc.), and other suchindustrial assets. These industrial assets are connected to a plantnetwork 116 (e.g., a common industrial protocol network, an Ethernet/IPnetwork, etc.) that facilitates data exchange between industrial deviceson the plant floor. Plant network 116 may be a wired or a wirelessnetwork. In the illustrated example, the high-level servers 1410 resideon a separate office network 108 that is connected to the plant network116 (e.g., through a router 1408 or other network infrastructuredevice).

In this example, IDE system 202 resides on a cloud platform 1406 andexecutes as a set of cloud-based IDE service 1402 that are accessible toauthorized remote client devices 1404. Cloud platform 1406 can be anyinfrastructure that allows shared computing services (such as IDEservices 1402) to be accessed and utilized by cloud-capable devices.Cloud platform 1406 can be a public cloud accessible via the Internet bydevices 1404 having Internet connectivity and appropriate authorizationsto utilize the IDE services 1402. In some scenarios, cloud platform 1406can be provided by a cloud provider as a platform-as-a-service (PaaS),and the IDE services 1402 can reside and execute on the cloud platform1406 as a cloud-based service. In some such configurations, access tothe cloud platform 1406 and associated IDE services 1402 can be providedto customers as a subscription service by an owner of the IDE services1402. Alternatively, cloud platform 1406 can be a private cloud operatedinternally by the industrial enterprise (the owner of the plantfacility). An example private cloud platform can comprise a set ofservers hosting the IDE services 1402 and residing on a corporatenetwork protected by a firewall.

Cloud-based implementations of IDE system 202 can facilitatecollaborative development by multiple remote developers who areauthorized to access the IDE services 1402. When a system project 302 isready for deployment, the project 302 can be commissioned to the plantfacility via a secure connection between the office network 108 or theplant network 116 and the cloud platform 1406. As discussed above, theindustrial IDE services 1402 can translate system project 302 toappropriate executable files—control program files 702, visualizationapplications 704, device configuration files 708, system configurationfiles 1412—and deploy these files to the appropriate devices in theplant facility to facilitate implementation of the automation project.

Although features of the industrial DSL have been described herein inthe context of IDE systems 202 having features discussed in connectionwith FIGS. 3-13 , it is to be appreciated that the DSL editor 224 andassociated editor definition component 210 described herein can becomponents of other types of IDEs that omit some or all of the featuresdescribed in connection with FIGS. 3-13 . That is, any IDE fordevelopment of industrial control code that supports the use ofindustrial DSLs, and customization thereof, is within the scope of oneor more embodiments of this disclosure.

The industrial DSL and associated DSL editor and editor definitioncomponent described herein render development of industrial control codemore efficient relative to platforms that only support ladder logicdevelopment, allowing programmers to generate industrial control codeusing a script-based DSL requiring fewer mouse clicks relative totraditional control programming environments. Dynamic feedback providedby the IDE's editing tools associated can guide the developer throughthe process of developing control code that complies with industry orin-house standards. Also, rendering a control program in both text-basedand graphical formats simultaneously within the same developmentinterface affords users a greater degree of flexibility in the manner inwhich program edits are submitted.

FIGS. 15-16 illustrate various methodologies in accordance with one ormore embodiments of the subject application. While, for purposes ofsimplicity of explanation, the one or more methodologies shown hereinare shown and described as a series of acts, it is to be understood andappreciated that the subject innovation is not limited by the order ofacts, as some acts may, in accordance therewith, occur in a differentorder and/or concurrently with other acts from that shown and describedherein. For example, those skilled in the art will understand andappreciate that a methodology could alternatively be represented as aseries of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with the innovation. Furthermore, interactiondiagram(s) may represent methodologies, or methods, in accordance withthe subject disclosure when disparate entities enact disparate portionsof the methodologies. Further yet, two or more of the disclosed examplemethods can be implemented in combination with each other, to accomplishone or more features or advantages described herein.

FIG. 15 illustrates an example methodology 1500 for rendering anindustrial control program in an industrial IDE development interfaceand receiving edits to the program. Initially, at 1502, an industrialcontrol program is displayed in a graphical format in a graphical editorwindow of an industrial IDE system. The graphical format maybe, forexample, ladder logic, a function block diagram, a sequential functionchart, or another graphical format. At 1504, the industrial controlprogram is also displayed in a text format in a text editor window ofthe industrial IDE system. The graphical editor window and the texteditor window are displayed simultaneously on a development interface ofthe industrial IDE system.

At 1506, a determination is made as to whether an edit to the industrialcontrol program is received via interaction with the graphical editorwindow. This edit can be received as a manipulation of the graphicalview of the program, such as by adding, deleting, moving or editingladder logic rungs and their associated program elements; changingparameter values associated with instruction blocks or other programelements; or other such graphical edits. If an edit is received viainteraction with the graphical editor window (YES at step 1506), themethodology proceeds to step 1510, where both the graphical view of thecontrol program in the graphical editor window and the text view of theindustrial control program in the text editor window are updated toreflect the edit, and the method returns to step 1502 and repeats.

If no edit to the industrial control program is received via interactionwith the graphical editor window (NO at step 1506), the methodologyproceeds to step 1508, where a determination is made as to whether anedit to the control program is received via interaction with the texteditor window. This edit can be received as a modification to one ormore lines of the text-based code. If an edit is received viainteraction with the text editor window (YES at step 1508), themethodology proceeds to step 1510, where both the graphical view of thecontrol program in the graphical editor window and the text view of theindustrial control program in the text editor window are updated toreflect the edit, and the method returns to step 1502 and repeats.

If no edit is received via interaction with the text editor window (NOat step 1508), the methodology returns to step 1502 and repeats.

FIG. 16 illustrates an example methodology 1600 for customizing aprogramming interface of an industrial IDE. At 1602, DSL definition datadefining an industrial DSL for use in developing industrial controlprojects is received. The DSL definition data can specify, for example,a syntax of the industrial DSL, definitions of automation objects thatcan be called within the industrial DSL (e.g., automation objectsrepresenting industrial assets such as machines, processes, controllers,drives, control programs, controller tags, etc.), parent-childrelationships between the automation objects, namespaces, mapping ofprogramming nomenclature, programming guardrails, code modules forfrequently programmed control tasks or applications (e.g., pumpingapplications, conveyor control applications, web tension controlapplications, etc.), or other such aspects of the industrial DSL. At1604, the development interface of the industrial IDE is customized inaccordance with the DSL definition data received at step 1602. Themethodology can then proceed to methodology 1500 described above inconnection with FIG. 15 , with any of the steps of that methodology 1500carried out in accordance with the customized industrial DSL defined bymethodology 1600. That is, display features of either of the graphicalor text formats displayed at steps 1502, 1504, or 1510 (e.g.,programmatic feedback, colors, highlighting, type-aheads,auto-corrections, auto-completions, etc.) can be defined at least inpart by the DSL definition data received at step 1602.

Embodiments, systems, and components described herein, as well ascontrol systems and automation environments in which various aspects setforth in the subject specification can be carried out, can includecomputer or network components such as servers, clients, programmablelogic controllers (PLCs), automation controllers, communicationsmodules, mobile computers, on-board computers for mobile vehicles,wireless components, control components and so forth which are capableof interacting across a network. Computers and servers include one ormore processors—electronic integrated circuits that perform logicoperations employing electric signals—configured to execute instructionsstored in media such as random access memory (RAM), read only memory(ROM), a hard drives, as well as removable memory devices, which caninclude memory sticks, memory cards, flash drives, external hard drives,and so on.

Similarly, the term PLC or automation controller as used herein caninclude functionality that can be shared across multiple components,systems, and/or networks. As an example, one or more PLCs or automationcontrollers can communicate and cooperate with various network devicesacross the network. This can include substantially any type of control,communications module, computer, Input/Output (I/O) device, sensor,actuator, and human machine interface (HMI) that communicate via thenetwork, which includes control, automation, and/or public networks. ThePLC or automation controller can also communicate to and control variousother devices such as standard or safety-rated I/O modules includinganalog, digital, programmed/intelligent I/O modules, other programmablecontrollers, communications modules, sensors, actuators, output devices,and the like.

The network can include public networks such as the internet, intranets,and automation networks such as control and information protocol (CIP)networks including DeviceNet, ControlNet, safety networks, andEthernet/IP. Other networks include Ethernet, DH/DH+, Remote I/O,Fieldbus, Modbus, Profibus, CAN, wireless networks, serial protocols,and so forth. In addition, the network devices can include variouspossibilities (hardware and/or software components). These includecomponents such as switches with virtual local area network (VLAN)capability, LANs, WANs, proxies, gateways, routers, firewalls, virtualprivate network (VPN) devices, servers, clients, computers,configuration tools, monitoring tools, and/or other devices.

In order to provide a context for the various aspects of the disclosedsubject matter, FIGS. 17 and 18 as well as the following discussion areintended to provide a brief, general description of a suitableenvironment in which the various aspects of the disclosed subject mattermay be implemented. While the embodiments have been described above inthe general context of computer-executable instructions that can run onone or more computers, those skilled in the art will recognize that theembodiments can be also implemented in combination with other programmodules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the inventive methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, Internet of Things (IoT)devices, distributed computing systems, as well as personal computers,hand-held computing devices, microprocessor-based or programmableconsumer electronics, and the like, each of which can be operativelycoupled to one or more associated devices.

The illustrated embodiments herein can be also practiced in distributedcomputing environments where certain tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules can be located inboth local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media, machine-readable storage media,and/or communications media, which two terms are used herein differentlyfrom one another as follows. Computer-readable storage media ormachine-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media or machine-readablestorage media can be implemented in connection with any method ortechnology for storage of information such as computer-readable ormachine-readable instructions, program modules, structured data orunstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, compact disk read only memory (CD-ROM), digitalversatile disk (DVD), Blu-ray disc (BD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, solid state drives or other solid statestorage devices, or other tangible and/or non-transitory media which canbe used to store desired information. In this regard, the terms“tangible” or “non-transitory” herein as applied to storage, memory orcomputer-readable media, are to be understood to exclude onlypropagating transitory signals per se as modifiers and do not relinquishrights to all standard storage, memory or computer-readable media thatare not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 17 , the example environment 1700 forimplementing various embodiments of the aspects described hereinincludes a computer 1702, the computer 1702 including a processing unit1704, a system memory 1706 and a system bus 1708. The system bus 1708couples system components including, but not limited to, the systemmemory 1706 to the processing unit 1704. The processing unit 1704 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 1704.

The system bus 1708 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1706includes ROM 1710 and RAM 1712. A basic input/output system (BIOS) canbe stored in a non-volatile memory such as ROM, erasable programmableread only memory (EPROM), EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer1702, such as during startup. The RAM 1712 can also include a high-speedRAM such as static RAM for caching data.

The computer 1702 further includes an internal hard disk drive (HDD)1714 (e.g., EIDE, SATA), one or more external storage devices 1716(e.g., a magnetic floppy disk drive (FDD) 1716, a memory stick or flashdrive reader, a memory card reader, etc.) and an optical disk drive 1720(e.g., which can read or write from a CD-ROM disc, a DVD, a BD, etc.).While the internal HDD 1714 is illustrated as located within thecomputer 1702, the internal HDD 1714 can also be configured for externaluse in a suitable chassis (not shown). Additionally, while not shown inenvironment 1700, a solid state drive (SSD) could be used in additionto, or in place of, an HDD 1714. The HDD 1714, external storagedevice(s) 1716 and optical disk drive 1720 can be connected to thesystem bus 1708 by an HDD interface 1724, an external storage interface1726 and an optical drive interface 1728, respectively. The interface1724 for external drive implementations can include at least one or bothof Universal Serial Bus (USB) and Institute of Electrical andElectronics Engineers (IEEE) 1394 interface technologies. Other externaldrive connection technologies are within contemplation of theembodiments described herein.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1702, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to respective types of storage devices, it should beappreciated by those skilled in the art that other types of storagemedia which are readable by a computer, whether presently existing ordeveloped in the future, could also be used in the example operatingenvironment, and further, that any such storage media can containcomputer-executable instructions for performing the methods describedherein.

A number of program modules can be stored in the drives and RAM 1712,including an operating system 1730, one or more application programs1732, other program modules 1734 and program data 1736. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1712. The systems and methods described herein can beimplemented utilizing various commercially available operating systemsor combinations of operating systems.

Computer 1702 can optionally comprise emulation technologies. Forexample, a hypervisor (not shown) or other intermediary can emulate ahardware environment for operating system 1730, and the emulatedhardware can optionally be different from the hardware illustrated inFIG. 17 . In such an embodiment, operating system 1730 can comprise onevirtual machine (VM) of multiple VMs hosted at computer 1702.Furthermore, operating system 1730 can provide runtime environments,such as the Java runtime environment or the .NET framework, forapplication programs 1732. Runtime environments are consistent executionenvironments that allow application programs 1732 to run on anyoperating system that includes the runtime environment. Similarly,operating system 1730 can support containers, and application programs1732 can be in the form of containers, which are lightweight,standalone, executable packages of software that include, e.g., code,runtime, system tools, system libraries and settings for an application.

Further, computer 1702 can be enable with a security module, such as atrusted processing module (TPM). For instance with a TPM, bootcomponents hash next in time boot components, and wait for a match ofresults to secured values, before loading a next boot component. Thisprocess can take place at any layer in the code execution stack ofcomputer 1702, e.g., applied at the application execution level or atthe operating system (OS) kernel level, thereby enabling security at anylevel of code execution.

A user can enter commands and information into the computer 1702 throughone or more wired/wireless input devices, e.g., a keyboard 1738, a touchscreen 1740, and a pointing device, such as a mouse 1742. Other inputdevices (not shown) can include a microphone, an infrared (IR) remotecontrol, a radio frequency (RF) remote control, or other remote control,a joystick, a virtual reality controller and/or virtual reality headset,a game pad, a stylus pen, an image input device, e.g., camera(s), agesture sensor input device, a vision movement sensor input device, anemotion or facial detection device, a biometric input device, e.g.,fingerprint or iris scanner, or the like. These and other input devicesare often connected to the processing unit 1704 through an input deviceinterface 1744 that can be coupled to the system bus 1708, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, a BLUETOOTH®interface, etc.

A monitor 1744 or other type of display device can be also connected tothe system bus 1708 via an interface, such as a video adapter 1746. Inaddition to the monitor 1744, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1702 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1748. The remotecomputer(s) 1748 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1702, although, for purposes of brevity, only a memory/storage device1750 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1752 and/orlarger networks, e.g., a wide area network (WAN) 1754. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1702 can beconnected to the local network 1752 through a wired and/or wirelesscommunication network interface or adapter 1756. The adapter 1756 canfacilitate wired or wireless communication to the LAN 1752, which canalso include a wireless access point (AP) disposed thereon forcommunicating with the adapter 1756 in a wireless mode.

When used in a WAN networking environment, the computer 1702 can includea modem 1758 or can be connected to a communications server on the WAN1754 via other means for establishing communications over the WAN 1754,such as by way of the Internet. The modem 1758, which can be internal orexternal and a wired or wireless device, can be connected to the systembus 1708 via the input device interface 1742. In a networkedenvironment, program modules depicted relative to the computer 1702 orportions thereof, can be stored in the remote memory/storage device1750. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

When used in either a LAN or WAN networking environment, the computer1702 can access cloud storage systems or other network-based storagesystems in addition to, or in place of, external storage devices 1716 asdescribed above. Generally, a connection between the computer 1702 and acloud storage system can be established over a LAN 1752 or WAN 1754e.g., by the adapter 1756 or modem 1758, respectively. Upon connectingthe computer 1702 to an associated cloud storage system, the externalstorage interface 1726 can, with the aid of the adapter 1756 and/ormodem 1758, manage storage provided by the cloud storage system as itwould other types of external storage. For instance, the externalstorage interface 1726 can be configured to provide access to cloudstorage sources as if those sources were physically connected to thecomputer 1702.

The computer 1702 can be operable to communicate with any wirelessdevices or entities operatively disposed in wireless communication,e.g., a printer, scanner, desktop and/or portable computer, portabledata assistant, communications satellite, any piece of equipment orlocation associated with a wirelessly detectable tag (e.g., a kiosk,news stand, store shelf, etc.), and telephone. This can include WirelessFidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, thecommunication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

FIG. 18 is a schematic block diagram of a sample computing environment1800 with which the disclosed subject matter can interact. The samplecomputing environment 1800 includes one or more client(s) 1802. Theclient(s) 1802 can be hardware and/or software (e.g., threads,processes, computing devices). The sample computing environment 1800also includes one or more server(s) 1804. The server(s) 1804 can also behardware and/or software (e.g., threads, processes, computing devices).The servers 1804 can house threads to perform transformations byemploying one or more embodiments as described herein, for example. Onepossible communication between a client 1802 and servers 1804 can be inthe form of a data packet adapted to be transmitted between two or morecomputer processes. The sample computing environment 1800 includes acommunication framework 1806 that can be employed to facilitatecommunications between the client(s) 1802 and the server(s) 1804. Theclient(s) 1802 are operably connected to one or more client datastore(s) 1808 that can be employed to store information local to theclient(s) 1602. Similarly, the server(s) 1604 are operably connected toone or more server data store(s) 1810 that can be employed to storeinformation local to the servers 1804.

What has been described above includes examples of the subjectinnovation. It is, of course, not possible to describe every conceivablecombination of components or methodologies for purposes of describingthe disclosed subject matter, but one of ordinary skill in the art mayrecognize that many further combinations and permutations of the subjectinnovation are possible. Accordingly, the disclosed subject matter isintended to embrace all such alterations, modifications, and variationsthat fall within the spirit and scope of the appended claims.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated exemplary aspects of the disclosed subjectmatter. In this regard, it will also be recognized that the disclosedsubject matter includes a system as well as a computer-readable mediumhaving computer-executable instructions for performing the acts and/orevents of the various methods of the disclosed subject matter.

In addition, while a particular feature of the disclosed subject mattermay have been disclosed with respect to only one of severalimplementations, such feature may be combined with one or more otherfeatures of the other implementations as may be desired and advantageousfor any given or particular application. Furthermore, to the extent thatthe terms “includes,” and “including” and variants thereof are used ineither the detailed description or the claims, these terms are intendedto be inclusive in a manner similar to the term “comprising.”

In this application, the word “exemplary” is used to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion.

Various aspects or features described herein may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, carrier, or media. For example, computerreadable media can include but are not limited to magnetic storagedevices (e.g., hard disk, floppy disk, magnetic strips . . . ), opticaldisks [e.g., compact disk (CD), digital versatile disk (DVD) . . . ],smart cards, and flash memory devices (e.g., card, stick, key drive . .. ).

What is claimed is:
 1. A system, comprising: a memory that storesexecutable components; and a processor, operatively coupled to thememory, that executes the executable components, the executablecomponents comprising: a user interface component configured to renderan integrated development environment (IDE) interface and to receive,via an interaction with the IDE interface, an industrial controlprogramming input that defines an industrial control program; and aproject generation component configured to generate, based on theindustrial control programming input, an executable control program filethat, in response to execution on an industrial controller, causes theindustrial controller to monitor and control an industrial automationsystem in accordance with the industrial control program, wherein theuser interface component is further configured to, in response toreceipt, via an interaction with either of a graphical editor window ora text editor window, of a program navigation input requesting displayof a selected portion of the industrial control program, simultaneouslydisplay the selected portion of the industrial control program in thegraphical editor window in a graphical format and in the text editorwindow in a text-based format.
 2. The system of claim 1, wherein the IDEinterface is configured to receive the industrial control programminginput in the graphical format via the interaction with the graphicaleditor window and in the text-based format via the interaction with thetext editor window.
 3. The system of claim 1, wherein the graphicalformat is at least one of ladder logic, a sequential function chart, ora function block diagram.
 4. The system of claim 1, wherein the userinterface component is configured to, in response to receipt of an editto the industrial control program via the interaction with either of thegraphical editor window or the text editor window, update respectiveviews of the industrial control program displayed in the graphicaleditor window and the text editor window in accordance with the edit. 5.The system of claim 1, wherein the user interface component isconfigured to receive at least a portion of the industrial controlprogramming input as an industrial domain-specific language (DSL) and torender a programming feedback in response to receipt of the industrialcontrol programming input.
 6. The system of claim 5, wherein theprogramming feedback comprises at least one of error highlighting,syntax highlighting, code snippet management feedback, type-aheadrecommendations, or programming suggestions.
 7. The system of claim 5,further comprising an editor definition component configured to receivea DSL definition input that defines programming features of theindustrial DSL and to configure at least one of the graphical editorwindow or the text editor window to support the programming featuresbased on the DSL definition input.
 8. The system of claim 7, wherein theprogramming features comprise at least one of a syntax of the industrialDSL, definitions of automation objects supported by the industrial DSL,parent-child relationships between the automation objects, a namespacesupported by the industrial DSL, or types of the programming feedbackrendered by the user interface component.
 9. The system of claim 1,wherein the graphical editor window and the text editor window supportinstantiation of automation objects within the industrial controlprogram, and the automation objects represent respective industrialassets including at least one of an industrial process, a controller, acontrol program, a tag within the control program, a machine, a motor, amotor drive, a telemetry device, a tank, a valve, a pump, an industrialsafety device, an industrial robot, or an actuator.
 10. The system ofclaim 1, wherein the graphical editor window is configured to render anautomation object, of the automation objects, in a graphical format, andthe text editor window is configured to render the automation object asa text string.
 11. A method, comprising: rendering, by a systemcomprising a processor, an integrated development environment (IDE)interface on a client device; receiving, by the system via aninteraction with the IDE interface, an industrial control programminginput that defines an industrial control program; and generating, by thesystem based on the industrial control programming input, an executablecontrol program file that, in response to execution on an industrialcontroller, causes the industrial controller to monitor and control anindustrial machine in accordance with the industrial control program,wherein the rendering comprises, in response to receipt, via aninteraction with either of a graphical editor window or a text editorwindow, of a program navigation input requesting display of a selectedportion of the industrial control program, simultaneously displaying, bythe system, the selected portion of the industrial control program inthe graphical editor window in a graphical format and in the text editorwindow in a text-based format.
 12. The method of claim 11, wherein thereceiving comprises: receiving a first portion of the industrial controlprogramming input in the graphical format via the interaction with thegraphical editor window, and receiving a second portion of theindustrial control programming in the text-based format via interactionwith the text editor window.
 13. The method of claim 11, wherein thegraphical format is at least one of ladder logic, a sequential functionchart, or a function block diagram.
 14. The method of claim 11, furthercomprising, in response to receipt of an edit to the industrial controlprogram via the interaction with either of the graphical editor windowor the text editor window, updating, by the system, respective views ofthe industrial control program displayed in the graphical editor windowand the text editor window in accordance with the edit.
 15. The methodof claim 11, further comprising: receiving, by the system, at least asubset of the industrial control programming input as an industrialdomain-specific language (DSL), and rendering, by the system, aprogramming feedback in response to receipt of the industrial controlprogramming input.
 16. The method of claim 15, wherein the programmingfeedback comprises at least one of error highlighting, syntaxhighlighting, code snippet management feedback, type-aheadrecommendations, or programming suggestions.
 17. The method of claim 15,further comprising: receiving, by the system, a DSL definition inputthat defines programming features of the industrial DSL; andconfiguring, by the system in response to receiving the DSL definitioninput, at least one of the graphical editor window or the text editorwindow to support the programming features defined by the DSL definitioninput.
 18. The method of claim 17, wherein the programming featurescomprise at least one of a syntax of the industrial DSL, definitions ofautomation objects supported by the industrial DSL, parent-childrelationships between the automation objects, a namespace supported bythe industrial DSL, or types of the programming feedback rendered by theuser interface component.
 19. A non-transitory computer-readable mediumhaving stored thereon instructions that, in response to execution, causea system comprising a processor to perform operations, the operationscomprising: rendering an integrated development environment (IDE)interface on a client device; receiving, via an interaction with the IDEinterface, an industrial control programming input that defines anindustrial control program; and generating, based on the industrialcontrol programming input, an executable control program file that, inresponse to execution on an industrial controller, causes the industrialcontroller to monitor and control an industrial automation system inaccordance with the industrial control program, wherein the renderingcomprises, in response to receiving, via an interaction with either of agraphical editor window or a text editor window, a program navigationinput requesting display of a selected portion of the industrial controlprogram, simultaneously displaying the selected portion of theindustrial control program in the graphical editor window in a graphicalformat and in the text editor window in a text-based format.
 20. Thenon-transitory computer-readable medium of claim 19, wherein theoperations further comprise, in response to receipt of an edit to theindustrial control program via the interaction with the graphical editorwindow, updating respective views of the industrial control programdisplayed in the graphical editor window and the text editor window inaccordance with the edit.